Liquidity Behavior Engine
The Liquidity Behavior Engine is built to read what the book is actually doing before price fully reacts. It brings pulling, stacking, aggressive participation, and vacuum conditions into one clean column so execution decisions feel structured instead of guessed.
Aggressive Sell Stacking Shows Intent.
The orange highlight marks aggressive sell stacking. This is not passive noise — it is a more forceful shift in offer-side behavior that helps frame when sellers are leaning with intent instead of simply sitting in the book.
Vacuum Conditions Explain Fast Price Travel.
The darker blue highlight marks a buy-side vacuum. When liquidity thins out, price can move aggressively through that zone. Instead of wondering why the move accelerated, you can see the lack of opposing liquidity in real time.
Sell-Side Pulling
IndianRed bars highlight buy-side pulling behavior, while DodgerBlue reflects sell-side pulling. Together they help expose when one side is quietly backing away instead of absorbing.
Buy Stacking
Cyan highlights show buy stacking. This helps separate actual support being built from random flicker in the book.
One Read, Not Five
Instead of scanning multiple separate tools, the engine compresses liquidity behavior into one focused execution column.
Use It With Your Structure, Not In Isolation.
The column becomes much stronger when paired with your chart context. In these examples, the Liquidity Behavior Engine sits beside structure and delta context so you can read whether the book agrees with the trade location you already care about.
Instead of memorizing colors, focus on what the behavior is telling you. The engine highlights shifts in participation, intent, and liquidity conditions so you can quickly judge whether buyers or sellers are in control.
A 2-in-1 Liquidity Read for Serious Execution.
The Liquidity Behavior Engine is not meant to be just another DOM visual. It is built to help read two core functions at once: liquidity intent and liquidity conditions. That gives CORE a stronger execution identity without cluttering the workflow.